In a 22.04 LXD container running SC7, running: # snapcraft help <plugin> fails if you are in the context of a snapcraft build directory whose snapcraft.yaml file refers to a core22 extension. As an example, if I am in an arbitrary directory in my container (say home), then this works: # snapcraft help catkin Displaying help for the 'catkin' plugin for 'core20'. The catkin plugin for ROS 1 parts. .. and so on ... However, if I happen to be in my ROS2/Humble project directory, where the snapcraft.yaml file incorporates the ros2-humble extension, then: # snapcraft help catkin Issues while validating snapcraft.yaml: The 'apps/ros2-talker-listener/extensions[0]' property does not match the required schema: 'ros2-humble' is not one of ['flutter-stable', 'flutter-beta', 'flutter-dev', 'flutter-master', 'gnome-3-28', 'gnome-3-34', 'gnome-3-38', 'kde-neon', 'ros1-noetic', 'ros2-foxy'] It seems clear(?) that, even though I am simply asking for some help, snapcraft insists on validating my snapcraft.yaml file and chokes on a core22 extension (this is already a known bug). This seems unnecessary -- simply asking for help should not dictate doing anything other than displaying that help.